Fiat Redemption Architecture & Interfacing Overview
When the Router selects a Fiat Redemption Route, the platform converts digital asset balance in the Source ADA (e.g., `ada_cust_usdc_01`) into a fiat payout to a Destination Fiat Account / ADA (e.g., `ada_cust_fiat_usd` or External Bank Account via Fedwire / ACH / Circle Fiat).
System Topology & ADA Interfacing Architecture
Click any component card to inspect its inputs, outputs, state machine impact, and subledger hooks.
Source ADA (Account of Digital Asset)
Internal Identifier: ada_cust_usdc_01
Holds customer's digital asset balance ($10,000 USDC). Manages Available, Reserved, and Pending Outbound subledger buckets during redemption.
Destination ADA / External Banking Target
Target Account: ada_cust_fiat_usd / Chase Bank Wire
The fiat entitlement destination. The system maps customer bank details (Routing #021000021, Acct #****4829) as a linked fiat instrument for payout.
Requests $10,000 USD fiat off-ramp payout to Chase Bank account.
State transition coordinator: created โ route_resolved โ pending_bank โ confirmed.
Evaluates profile `RP_FIAT_REDEMPTION_V1`. Scores ACH, Fedwire, and Circle Fiat rails.
Locks USD:USDC 1:1 redemption rate ($10,000 USDC = $10,000 USD) and checks off-ramp limits.
Inspects Source ADA available USDC ($10,000) and Bank Custody reserves ($500k USD).
Executes balanced subledger journals across Available, Reserved, and Fiat Transit liabilities.
Subledger ADA holding digital assets. Encumbers $10k during redemption phase.
Stores append-only financial journals. Debits equal credits at all times.
Pipes payout instructions to commercial bank host-to-host API / ISO20022 wire gateway.
Executes wire transfer from platform custody bank to recipient's Chase account.
Ingests BAI2/CAMT.053 bank confirmation files and real-time wire status webhooks.
Matches Federal IMAD/OMAD reference numbers against instruction IDs to finalize settlement.
Select a component node above
Click on any component card in the topology diagram to inspect its interface details, triggered events, and database interactions.